Playback Device Control

ABSTRACT

Examples described herein involve a playback device performing one or more playback device actions based on locations of one or more physical contacts on an external surface of the playback device. A processor of the playback device may receive from an array of proximity sensors underlying an external surface of the playback device, location data indicating a physical contact at a location on the external surface. Based on at least the location, the processor may identify a playback device action from a plurality of playback device actions, and cause at least the playback device to perform the identified playback device action. The playback device may further include at least one orientation sensor from which the processor may also receive orientation data indicating an orientation of the playback device. The processor may identify the playback device action also based on the orientation of the playback device.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/612,023 entitled “Playback Device with Capacitive Sensors” toGriffiths et al., filed Jun. 2, 2017, which is a continuation of U.S.application Ser. No. 14/500,465 entitled “Playback Device Control” toGriffiths et al., filed Sep. 29, 2014 and issued on Jun. 6, 2017 as U.S.Pat. No. 9,671,780, the disclosures of which are incorporated herein byreference in their entireties.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when SONOS, Inc. filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The Sonos Wireless HiFi System enablespeople to experience music from a plethora of sources via one or morenetworked playback devices. Through a software control applicationinstalled on a smartphone, tablet, or computer, one can play what he orshe wants in any room that has a networked playback device.Additionally, using the controller, for example, different songs can bestreamed to each room with a playback device, rooms can be groupedtogether for synchronous playback, or the same song can be heard in allrooms synchronously.

Given the ever growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5A shows example external surfaces of a playback device;

FIG. 5B shows example regions on an external surface of a playbackdevice;

FIG. 6 shows an example flow diagram of a first method for performing aplayback device action based on a physical contact on an externalsurface of a playback device;

FIG. 7A shows a first example orientation of a playback device;

FIG. 7B shows a second example orientation of a playback device;

FIG. 7C shows a third example orientation of a playback device; and

FIG. 8 shows an example flow diagram of a second method for performing aplayback device action based on a physical contact on an externalsurface of a playback device.

The drawings are for the purpose of illustrating example embodiments,but it is understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

In some cases, a playback device may be controlled using a controllerdevice and/or buttons on the playback device. However, if a user wantsto conveniently provide a certain control command to the playbackdevice, accessing a user interface provided by a controller applicationon the controller device to provide the control command, or locating andidentifying a button on the playback device, then pressing the button toprovide the control command, may be relatively burdensome.

Examples discussed herein involve a playback device performing one ormore playback device actions based on locations of one or moreinteractions (i.e. physical contacts and/or physical presences) on ornear (i.e. within a predetermined proximal distance from) an externalsurface of the playback device. In other words, the playback device maybe controlled, at least to some extent, by one or more touches on theplayback device. In a case the playback device is one of a group ofplayback devices configured to play media content in synchrony, theother playback devices in the group may also perform the one or moreplayback device actions. In another case, one or more other playbackdevices in communication with the playback device may also perform theone or more playback device actions whether or not they are part of agroup of playback devices configured to play media in synchrony with theplayback device.

Accordingly, the user may provide the certain control commands bytouching certain locations or regions on the external surface of theplayback device, without needing to access the user interface or locateand identify specific buttons.

In one example, the playback device may have an array of proximitysensors underlying an external surface of the playback device. The arrayof proximity sensors may include one or more types of sensors configuredto detect proximal movement or contact on the external surface of theplayback device. The external surface may include any one or moresurfaces on the playback device that is substantially perpendicular to aspeaker grill of the playback device. The speaker grill of the playbackdevice may be on a side of the playback device where outward-facingspeakers of the playback device are positioned.

In one case, the external surface of the playback device may include twoor more regions. In one instance, a first subset of the array ofproximity sensors may underlie a first region of the external surface,and a second subset of the array of proximity sensor may underlie asecond region of the external surface.

In one example, a processor of the computing device may receive from thearray of proximity sensors, location data indicating a physical contactat a location on the external surface. In one case, the location datamay indicate which one or more proximity sensors in the array ofproximity sensors detected the physical contact. Based on locations ofthe one or more proximity sensors that detected the physical contact,the processor may determine whether the physical contact occurred on thefirst region of the external surface or the second region of theexternal surface.

Based on at least the location and/or the region of the physicalcontact, the processor may identify a playback device from a pluralityof playback device actions. The plurality of playback device actions mayinclude beginning playback of media content, pausing playback of mediacontent, increasing a playback volume of the playback device, anddecreasing a playback volume of the playback device, among otherpossibilities.

In one example, if the location of the detected physical is in the firstregion of the external surface, the processor may identify the playbackdevice action of increasing the playback volume of the playback device.On the other hand, if the location of the detected physical contact isin the second region of the external surface, the processor may identifythe playback device of decreasing the playback volume of the playbackdevice. Other examples are also possible.

Upon identifying the playback device action, the processor may thencause at least the playback device to perform the identified playbackdevice action. For instance, if the identified playback device action isto increase the playback volume of the playback device, the processormay cause the playback volume of the playback device to increase.

The playback device action may be identified further based on additionaldata received from the array of proximity sensors and/or data receivedfrom other components in the playback device. In one example, additionaldata received from the array of proximity sensors may indicate a type ofthe physical contact. In one instance, the physical contact may be asingle tap at a single location or a swipe that traverses multiplelocations. In some cases, the swipe may traverse locations in both thefirst and second regions of the external surface. In another instance,the physical contact may be one of two or more concurrent physicalcontacts. In a further instance, the physical contact may be one of twoor more successive physical contacts making up a sequence of singletaps, or one or more double-taps. Other examples are also possible.

In one example, the playback device may further include at least oneorientation sensor configured to provide orientation data that indicatesan orientation of the playback device. In a first orientation of theplayback device, the first region of the external surface may be abovethe second region of the external surface, while in a second orientationof the playback device, the second region of the external surface may beabove the first region of the external surface.

The processor may accordingly identify the playback device actionfurther based on the orientation of the playback device. In one case,the processor may identify the playback device action of increasing theplayback volume of the playback device based on a physical contact at alocation in the first region while the playback device is in the firstorientation. On the other hand, the processor may identify the playbackdevice action of decreasing the playback volume of the playback devicebased on a physical contact at the location in the first region whilethe playback device is in the second orientation.

In another example, the processor may identify the playback deviceaction further based on a playback state of the playback device. In onecase, the processor may identify the playback device action of pausingplayback of media content based on a physical contact at a location inthe first region while the playback device is playing media content. Onthe other hand, the processor may identify the playback device action ofbeginning playback of media content based on the physical contact at thelocation in the first region while the playback device is not playingmedia content.

In yet another example, the processor may identify the playback deviceaction further based on whether the playback device is in motion. Motionof the playback device may be determined based on data received from theat least one orientation sensor in the playback device.

In one case, the processor may identify the playback device action ofincreasing a playback volume based on a physical contact at a locationin the first region while the playback device is not in motion. On theother hand, the processor may identify a playback device action of“null” or no action based on a physical contact at the location in thefirst region while the playback device is in motion. In other words, oneor more playback device actions may be disabled or deactivated while theplayback device is in motion.

In some cases, the array of proximity sensors or a subset of the arrayof proximity sensors may be deactivated while the playback device is inmotion. Accordingly, the processor may receive no data from the array ofproximity sensors while the playback device is in motion. Other examplesare also possible.

In some cases, the playback device may be part of a group of playbackdevices configured to play media content in synchrony. In such a case,some or all identified playback device actions may also be performed byother playback devices in the group of playback devices. For instance,if the playback device action of pausing playback of media content isidentified, the processor may cause playback of media content by allplayback devices in the group of the playback device to be paused.Further in some cases, the plurality of playback device actions that maybe identified based on one or more detected physical contacts may alsoinclude adding the playback device to a group of playback devices and/orremove the playback device from the group of playback devices. Otherexamples are also possible.

As indicated above, the present discussions involve a playback deviceperforming one or more playback device actions based on locations of oneor more physical contacts on an external surface of the playback device.In one aspect, a playback device is provided. The playback deviceincludes an array of proximity sensors underlying an external surface ofthe playback device. The external surface is substantially perpendicularto a speaker grill of the playback device. The playback device furtherincludes a processor, and memory having stored thereon instructionsexecutable by the processor to cause the processor to perform functionsincluding receiving from the array of proximity sensors, location dataindicating a physical contact at a location on the external surface,based on at least the location, identifying a playback device actionfrom a plurality of playback device actions, and causing at least theplayback device to perform the identified playback device action.

In another aspect, a playback device is provided. The playback deviceincludes an array of proximity sensors underlying an external surface ofthe playback device. The external surface is substantially perpendicularto a speaker grill of the playback device. The playback device alsoincludes at least one orientation sensor, a processor, and memory havingstored thereon instructions executable by the processor to cause theprocessor to perform functions including receiving from the at least oneorientation sensor, orientation data indicating an orientation of theplayback device, receiving from the array of proximity sensors, locationdata indicating a physical contact at a location on the externalsurface, based on at least (i) the orientation of the playback deviceand (ii) the location on the external surface, identifying a playbackdevice action from a plurality of playback device actions, and causingat least the playback device to perform the identified playback deviceaction.

In a further aspect, a non-transitory computer readable medium isprovided. The non-transitory computer readable medium has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions including receiving from an array ofproximity sensors underlying an external surface of a playback device,location data indicating a physical contact at a location on theexternal surface, based on at least the location, identifying a playbackdevice action from a plurality of playback device actions, and causingat least the playback device to perform the identified playback deviceaction.

While some examples described herein may refer to functions performed bygiven actors such as “users” and/or other entities, it should beunderstood that this is for purposes of explanation only. The claimsshould not be interpreted to require action by any such example actorunless explicitly required by the language of the claims themselves. Itwill be understood by one of ordinary skill in the art that thisdisclosure includes numerous other embodiments.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 inwhich one or more embodiments disclosed herein may be practiced orimplemented. The media playback system 100 as shown is associated withan example home environment having several rooms and spaces, such as forexample, a master bedroom, an office, a dining room, and a living room.As shown in the example of FIG. 1, the media playback system 100includes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130.

Further discussions relating to the different components of the examplemedia playback system 100 and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100, technologies described herein are not limitedto applications within, among other things, the home environment asshown in FIG. 1. For instance, the technologies described herein may beuseful in environments where multi-zone audio may be desired, such as,for example, a commercial setting like a restaurant, mall or airport, avehicle like a sports utility vehicle (SUV), bus or car, a ship or boat,an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100 of FIG. 1. The playback device200 may include a processor 202, software components 204, memory 206,audio processing components 208, audio amplifier(s) 210, speaker(s) 212,microphone(s) 220, and a network interface 214 including wirelessinterface(s) 216 and wired interface(s) 218. In one case, the playbackdevice 200 may not include the speaker(s) 212, but rather a speakerinterface for connecting the playback device 200 to external speakers.In another case, the playback device 200 may include neither thespeaker(s) 212 nor the audio amplifier(s) 210, but rather an audiointerface for connecting the playback device 200 to an external audioamplifier or audio-visual receiver.

In one example, the processor 202 may be a clock-driven computingcomponent configured to process input data according to instructionsstored in the memory 206. The memory 206 may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor 202. For instance, the memory 206 may be data storage thatcan be loaded with one or more of the software components 204 executableby the processor 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other embodiments are also possible.

The audio processing components 208 may include one or more ofdigital-to-analog converters (DAC), analog-to-digital converters (ADC),audio preprocessing components, audio enhancement components, and adigital signal processor (DSP), among others. In one embodiment, one ormore of the audio processing components 208 may be a subcomponent of theprocessor 202. In one example, audio content may be processed and/orintentionally altered by the audio processing components 208 to produceaudio signals. The produced audio signals may then be provided to theaudio amplifier(s) 210 for amplification and playback through speaker(s)212. Particularly, the audio amplifier(s) 210 may include devicesconfigured to amplify audio signals to a level for driving one or moreof the speakers 212. The speaker(s) 212 may include an individualtransducer (e.g., a “driver”) or a complete speaker system involving anenclosure with one or more drivers. A particular driver of thespeaker(s) 212 may include, for example, a subwoofer (e.g., for lowfrequencies), a mid-range driver (e.g., for middle frequencies), and/ora tweeter (e.g., for high frequencies). In some cases, each transducerin the one or more speakers 212 may be driven by an individualcorresponding audio amplifier of the audio amplifier(s) 210. In additionto producing analog signals for playback by the playback device 200, theaudio processing components 208 may be configured to process audiocontent to be sent to one or more other playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The microphone(s) 220 may include an audio sensor configured to convertdetected sounds into electrical signals. The electrical signal may beprocessed by the audio processing components 208 and/or the processor202. The microphone(s) 220 may be positioned in one or more orientationsat one or more locations on the playback device 200. The microphone(s)220 may be configured to detect sound within one or more frequencyranges. In one case, one or more of the microphone(s) 220 may beconfigured to detect sound within a frequency range of audio that theplayback device 200 is capable or rendering. In another case, one ormore of the microphone(s) 220 may be configured to detect sound within afrequency range audible to humans. Other examples are also possible.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. In one example, the audio content andother signals transmitted and received by the playback device 200 may betransmitted in the form of digital packet data containing an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 214 may be configured to parse thedigital packet data such that the data destined for the playback device200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), control device(s)within a data network the playback device 200 is associated with) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4Gmobile communication standard, and so on). The wired interface(s) 218may provide network interface functions for the playback device 200 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 802.3). While the networkinterface 214 shown in FIG. 2 includes both wireless interface(s) 216and wired interface(s) 218, the network interface 214 may in someembodiments include only wireless interface(s) or only wiredinterface(s).

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”) may further playaudio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it is understood that aplayback device is not limited to the example illustrated in FIG. 2 orto the SONOS product offerings. For example, a playback device mayinclude a wired or wireless headphone. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100 may be established withone or more playback zones, after which one or more zones may be added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100 may be dynamically modified, and in some embodiments, the mediaplayback system 100 supports numerous configurations. For instance, if auser physically moves one or more playback devices to or from a zone,the media playback system 100 may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already a playback zone, a new playback zone may be created for theparticular area.

Further, different playback zones of the media playback system 100 maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the dining room zone and the kitchen zone114 may be combined into a zone group for a dinner party such thatplayback devices 112 and 114 may render audio content in synchrony. Onthe other hand, the living room zone may be split into a television zoneincluding playback device 104, and a listening zone including playbackdevices 106, 108, and 110, if the user wishes to listen to music in theliving room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100. As shown, the control device 300may include a processor 302, memory 304, a network interface 306, a userinterface 308, and microphone(s) 310. In one example, the control device300 may be a dedicated controller for the media playback system 100. Inanother example, the control device 300 may be a network device on whichmedia playback system controller application software may be installed,such as for example, an iPhone™, iPad™ or any other smart phone, tabletor network device (e.g., a networked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant tofacilitating user access, control, and configuration of the mediaplayback system 100. The memory 304 may be configured to storeinstructions executable by the processor 302 to perform those functions.The memory 304 may also be configured to store the media playback systemcontroller application software and other data associated with the mediaplayback system 100 and the user.

The microphone(s) 310 may include an audio sensor configured to convertdetected sounds into electrical signals. The electrical signal may beprocessed by the processor 302. In one case, if the control device 300is a device that may also be used as a means for voice communication orvoice recording, one or more of the microphone(s) 310 may be amicrophone for facilitating those functions. For instance, the one ormore of the microphone(s) 310 may be configured to detect sound within afrequency range that a human is capable of producing and/or a frequencyrange audible to humans. Other examples are also possible.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 4G mobile communication standard, and so on). Thenetwork interface 306 may provide a means for the control device 300 tocommunicate with other devices in the media playback system 100. In oneexample, data and information (e.g., such as a state variable) may becommunicated between control device 300 and other devices via thenetwork interface 306. For instance, playback zone and zone groupconfigurations in the media playback system 100 may be received by thecontrol device 300 from a playback device or another network device, ortransmitted by the control device 300 to another playback device ornetwork device via the network interface 306. In some cases, the othernetwork device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100 may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100, byproviding a controller interface such as the controller interface 400shown in FIG. 4. The controller interface 400 includes a playbackcontrol region 410, a playback zone region 420, a playback status region430, a playback queue region 440, and an audio content sources region450. The user interface 400 as shown is just one example of a userinterface that may be provided on a network device such as the controldevice 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1)and accessed by users to control a media playback system such as themedia playback system 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100. In some embodiments, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100 of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some embodiments, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100 of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

The above discussions relating to playback devices, controller devices,playback zone configurations, and media content sources provide onlysome examples of operating environments within which functions andmethods described below may be implemented. Other operating environmentsand configurations of media playback systems, playback devices, andnetwork devices not explicitly described herein may also be applicableand suitable for implementation of the functions and methods.

III. Example Playback Device Control Based on Physical Interactions witha Playback Device

As indicated above, some examples discussed herein relate to a playbackdevice performing one or more playback device actions based on locationsof one or more physical interactions (i.e. physical contacts and/orphysical presences) on or near (i.e. within a predetermined proximaldistance from) an external surface of the playback device. FIG. 5A showsan example of a playback device 500 that has an external surfaceconfigured to detect the one or more physical contacts and that mayperform the one or more playback device actions based on locations ofthe detected one or more physical contacts. The playback device 500 maybe similar to the playback device 200 of FIG. 2, and may operate as apart of a media playback system, such as the media playback system 100shown in FIG. 1.

The playback device 500 has a speaker grill 510 and an external surface.The speaker grill 510 may cover a side of the playback device 500 whereoutward facing speakers of the playback device 500 may be positioned.The external surface may include a first surface 502 and a secondsurface 504, each of which, as shown, may be substantially perpendicularto the speaker grill 510. The external surface may also include a thirdsurface 506 and a fourth surface 508 that, in FIG. 5A are obscured bythe speaker grill 510 and a body of the playback device 500. In somecases, the external surface may further include a back surface of theplayback device 500 (not shown), opposite the speaker grill 510.

FIG. 5B shows an alternate view of the playback device 500 from abovethe playback device 500. In other words, FIG. 5B shows the first surface502 of the playback device 500. As shown, the first surface 502 mayinclude a first region 552, a second region 554, and a third region 556.Also shown in FIG. 5B is an array of proximity sensors (each representedas a circle) underlying the external surface of the playback device 500.In this case, a first subset of the array of proximity sensors mayunderlie the first region 552 of the first surface 502, a second subsetof the array of proximity sensors may underlie the second region 556 ofthe first surface 502, and a third subset of the array of proximitysensors may underlie the third region 556 of the first surface 502.

The array of proximity sensors may include one or more types ofproximity sensors. For instance, the array of proximity sensors mayinclude one or more capacitive sensors, one or more resistance sensors,one or more Piezo sensors, one or more infrared sensors, one or moreinductive sensors, one or more magnetic sensors, and one or more opticalsensors, among other possibilities. The array of proximity sensors maybe configured to detect physical contact on the first, second, or thirdregions on the first surface 502. In some cases, the array of proximitysensors may further be configured to detect presence or movement withina proximal distance of the first region 552, second region 554 or thirdregion 556 on the first surface 502. In one case, the one or more typesof proximity sensors in the array of proximity sensors may be selectedbased on a type of material of the first surface 502 and/or aconstruction of the playback device. Other examples are also possible.

FIG. 6 shows an example flow diagram of a first method 600 forperforming a playback device action based on a physical contact on anexternal surface of a playback device. Method 600 shown in FIG. 6presents an embodiment of a method that can be implemented within anoperating environment involving, for example, the media playback system100 of FIG. 1, one or more of the playback device 200 of FIG. 2, and oneor more of the playback device 500 of FIGS. 5A and 5B. In one example,the method 600 may be performed by a playback device, such as theplayback device 200 of FIG. 2, or the playback device 500 of FIGS. 5Aand 5B. In particular, the method 600 may be performed by a processor ofthe playback device, such as the processor 202 of the playback device200, or a processor of the playback device 500. In another example, themethod 600 may alternatively be performed in whole or in part by acomputing device, such as a server in communication with the playbackdevice.

Method 600 may include one or more operations, functions, or actions asillustrated by one or more of blocks 602-606. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.In addition, for the method 600 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive.

The computer readable medium may include non-transitory computerreadable medium, for example, such as computer-readable media thatstores data for short periods of time like register memory, processorcache and Random Access Memory (RAM). The computer readable medium mayalso include non-transitory media, such as secondary or persistent longterm storage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 600 and other processes and methods disclosedherein, each block may represent circuitry that is wired to perform thespecific logical functions in the process.

As shown in FIG. 6, the method 600 involves receiving from an array ofproximity sensors, data indicating a physical contact at a location onan external surface of a playback device at block 602, based on at leastthe location, identifying a playback device action from a plurality ofplayback device actions at block 604, and causing at least the playbackdevice to perform the identified playback device action at block 606.

At block 602, the method 600 involves receiving from an array ofproximity sensors, data indicating a physical contact at a location onan external surface of a playback device. Referring to the playbackdevice 500, one or more of the array of proximity sensors underlying thefirst surface 502 may be configured to output data based on proximitysensing by respective proximity sensors. In one example, a proximitysensor in the array of proximity sensors may output data indicating afirst value when no physical contact is detected by the proximitysensor, or output data indicating a second value when physical contactis detected by the proximity sensor. Accordingly, if the processor ofthe playback device 500 receives from a particular proximity sensor,data indicating the second value, the processor may determine thatphysical contact on the external surface of the playback device 500 wasdetected at a location within a range of the particular proximitysensor. In other words, the processor of the playback device 500 maydetermine the location of the physical contact on the external surfacebased on which of the array of proximity sensors outputted dataindicating the second value. Other examples are also possible.

In addition to the location of the physical contact on the externalsurface, data outputted by one or more of the array of proximity sensorsmay further indicate other characteristics of the physical contact aswell. In one example, the processor may receive from the array ofproximity sensors, touch data indicating an initiation of the physicalcontact with the external surface. In one case, the initiation of thephysical contact may be indicated when a particular physical contact isdetected at a certain location without any physical contact detected atany locations adjacent to the certain location prior to the detection ofthe particular physical contact.

In another example, the processor may receive from the array ofproximity sensors, release data indicating a termination of the physicalcontact with the external surface. In one case, the termination of thephysical contact may be indicated when a particular physical contact isterminated at a certain location without any substantially immediate,subsequent physical contact detected at any locations adjacent to thecertain location. Other examples are also possible.

In one example, the characteristics of the physical contact may alsoinclude a time duration of the physical contact. The time duration ofthe physical contact may be determined based on a duration of timebetween the initiation of physical contact and the termination of thephysical contact. In one case, the physical contact may be characterizedas a “tap” if the time duration of the physical contact is within apredetermined time duration range. For instance, the physical contactmay be characterized as a tap if the time duration of the physicalcontact is between 40 milliseconds and 160 milliseconds. In some cases,

In another case, the physical contact may be characterized as a “touchand hold” if the time duration of the physical contact is beyond thepredetermined time duration range. For instance, the physical contactmay be characterized as a tap and hold if the time duration of thephysical contact is beyond 160 milliseconds.

In another example, if a second physical contact is detected after atermination of the first physical contact, characteristics of the secondphysical contact, the first physical contact, or the combination of thefirst and second physical contacts may include the duration of timebetween the termination of the first physical contact and the initiationof the second physical contact. In one case, the physical contact may becharacterized as a “double-tap” if the initiation of the second physicalcontact occurs within a predetermined time duration after thetermination of the first physical contact. For instance, the two tapsmay be characterized as a double-tap if the time duration between thetwo taps is less than 90 milliseconds.

As indicated above, the array of proximity sensors may further beconfigured to detect presence or movement within a proximal distance ofthe first region 552, second region 554 or third region 556 on the firstsurface 502. In one case, the two taps may be characterized as adouble-tap further based on if a physical presence is within apredetermined proximal range of the external surface between the twotaps. For instance, the two taps may be characterized as a double-tap ifthe physical presence remains within 8 mm from the external surfacebetween the two taps.

In a further example, the physical contact on the external surface ofthe playback device 500 may traverse multiple locations on the externalsurface between the initiation of the physical contact and thetermination of the physical contact. In one case, characteristics of thephysical contact may include a direction of the traversal of thephysical contact and/or a distance of the traversal of the physicalcontact. In one case, the physical contact may be characterized as a“swipe” if the physical contact traverses a predetermined minimumdistance in a consistent direction. For instance, the physical contactmay be characterized as a swipe if the physical contact traverses atleast 20 millimeters on the external surface, along a primary axis ofthe array of proximity sensors. In some cases, the physical contact maybe characterized as a swipe also based on a time duration of thephysical contact. For instance, the physical contact may becharacterized as a swipe only if the time duration of the physicalcontact is between 40 milliseconds and 800 milliseconds.

In some examples, concurrent physical contacts with the external surfacemay be detected by the array of proximity sensors. In some cases, theconcurrent physical contact may be characterized together. For instance,if the concurrent physical contacts include two substantially concurrenttaps, the concurrent physical contacts may be characterized as a “dualtap” rather than two individual, unrelated taps. In another instance, ifthe concurrent physical contacts include two substantially concurrentswipes, rather than being characterized as two individual, unrelatedswipes, the concurrent physical contacts may be characterized as a “dualswipe” if the swipes are in substantially the same direction, a “pinch”if the swipes are in opposite directions towards each other, or a“stretch” if the swipes are in opposite directions away from each other.Other examples are also possible.

At block 604, the method 600 involves based on at least the location,identifying a playback device action from a plurality of playback deviceactions. Referring to the playback device 500 shown in FIG. 5B, a firstplayback device action may be identified if the physical contact isdetected at a location in the first region 552, a second playback deviceaction may be identified if the physical contact is detected at alocation in the second region 554, and a third playback device actionmay be identified if the third physical contact is detected at alocation in the third region 556.

In addition to the location of the physical contact, the playback deviceaction may also be identified based on characteristics of the physicalcontact, a configuration of the playback device, and/or a playback stateof the playback device. In one example, if the first playback deviceaction is identified based on a tap physical contact detected in thefirst region 552, a fourth playback device action may be identifiedbased on a double tap physical contact detected in the first region 552.In another example, if the first playback device action is identifiedbased on a physical contact detected in the first region 552 while theplayback device 500 is playing media content by itself, a fifth playbackdevice action may be identified based on a physical contact detected inthe first region 552 while the playback device 500 is playing mediacontent as a part of a stereo pair of playback devices. In a furtherexample, if the first playback device action is identified based on aphysical contact detected in the first region 552 while the playbackdevice is playing media content, a sixth playback device action may beidentified based on a physical contact detected in the first region 552while the playback by the playback device 500 is paused. Other examplesare also possible.

For illustration purposes, the plurality of playback device actions fromwhich the playback device action may be identified, may include (a)begin playback of media content, (b) pause playback of media content,(c) begin playback of a next media content in a playback queue of theplayback device 500, (d) begin playback of a previous media content inthe playback queue of the playback device 500, (e) restarting playbackof media content being played by the playback device 500, (f) increasinga playback volume, (g) decreasing a playback volume, (h) replacing mediacontent in the playback queue of the playback device 500 with apredetermined one or more media content, (i) disabling one or moreplayback device actions, and (j) enabling one or more playback deviceactions.

In some cases, as indicated throughout this discussion, the playbackdevice 500 may be capable of playing media content by itself, or insynchrony with one or more other playback devices in a media playbacksystem. As such, the plurality of playback device actions may furtherinclude (a) grouping of the playback device 500 with one or more otherplayback devices in a media playback system and (b) ungrouping of theplayback device 500 from one or more other playback devices in the mediaplayback system.

As indicated above, the playback device 500 may be one of a plurality ofplayback device in the media playback system and/or one of a subset ofthe plurality of playback devices playing media content in synchrony. Insuch a case, the plurality of playback device actions may include (a)begin playback of media content by the plurality of playback devices,(d) pause playback of media content by the plurality of playbackdevices, (e) begin playback of a next media content in a playback queueassociated with the plurality of playback devices, (f) begin playback ofa previous media content in the playback queue associated with theplurality of playback devices, (g) restarting playback of media contentbeing played by the plurality of playback devices, (f) increasing aplayback volume of the plurality of playback devices, (g) decreasing aplayback volume of the plurality of playback devices, (h) replacingmedia content in the playback queue associated with the plurality ofplayback devices with a predetermined one or more media content, (i)disabling one or more playback device actions by the plurality ofplayback devices, and (j) enabling one or more playback device actionsby the plurality of playback devices. Other examples are also possible.

As mentioned above, a respective playback device action in the pluralityof playback device actions may correspond to one or more characteristicsof a detected physical contact, such as a location of the physicalcontact, a configuration of the playback device 500, and/or a playbackstate of the playback device 500, among others. Accordingly, therespective playback device action may be identified based on the one ormore characteristics of the detected physical contact.

Provided in Table 1 are illustrative examples of physical contactcharacteristics and respective playback device actions. One havingordinary skill in the art will appreciate that these are forillustration purposes only, and that other combinations and examples arealso possible.

TABLE 1 Detected Physical Contact Characteristic(s) and Playback DeviceState Playback Device Action 1 Tap in second region 554; Begin playbackPlayback paused 2 Tap in second region 554; Pause playback Playbackongoing 3 Tap in first region 552 Decrease playback volume by 1 4 Tap inthird region 556 Increase playback volume by 1 5 Touch and hold in firstregion Decrease playback volume by 2 552 every 160 milliseconds 6 Touchand hold in third region Increase playback volume by 2 556 every 160milliseconds 7 Double tap in second region Begin playback of next trackin 554; Playback paused playback queue 8 Double tap in second regionSkip to next track in playback 554; Playback ongoing queue 9 Swipe fromleft to right across Skip to next track in playback second region 554(or from first queue region 552 to third region 556) 10 Swipe from rightto left across Skip to previous track in second region 554 (or fromthird playback queue region 556 to first region 552) 11 Dual swipe fromleft to right Fast forward track 15 seconds across second region 554 (orfrom first region 552 to third region 556) 12 Dual swipe from right toleft Rewind track 15 seconds across second region 554 (or from thirdregion 556 to first region 552) 13 Pinch from first region 552 andSeparate playback device from third region 556 to second zone group ofplayback devices. region 554 14 Stretch from second region Groupplayback device with 554 to first region 552 and other playback devicesthird region 556

At block 606, the method 600 involves causing at least the playbackdevice to perform the identified playback device action. In one example,if a playback device action of skipping to a next track in a playbackqueue, the processor may cause the playback device 500 to skip to thenext track in the playback queue. In one case, block 606 may beperformed in response to a playback device action identified at block604.

As suggested previously, if the playback device 500 is a part of a zonegroup, the processor may further cause each of the other playbackdevices in the zone group to perform the same, or a correspondingplayback device action. In such a case, the processor may furthertransmit to the other playback devices in the zone group, eitherdirectly or via a group coordinator of the zone group, a message tocause the other playback devices to skip to the next track in theplayback queue.

Referring to Table 1, a tap in the first region 552 may correspond toincreasing the playback volume by 1. In one case, if the playback device500 is a part of a zone group, the tap in the first region 552 maycorrespond to increasing the playback volume by 1 by each of theplayback devices in the zone group. In another case, only the playbackvolume of the playback device 500 is increased by 1. In such a case,another physical contact characteristic may correspond to increasing theplayback volume by 1 by each of the other playback devices in the zonegroup. For instance, a dual tap in the first region 552 may correspondto an increase of playback volume by 1 for all playback devices in thezone group, including the playback device 500. Other examples are alsopossible.

In one example, the playback device 500, and/or other playback devicesin a zone group with the playback device, if applicable may furtherprovide feedback indicating that the physical contact was detectedand/or that a corresponding playback device action has been identifiedand perform. For example, if the playback device 500 has one or moreLEDs external to the playback device 500, the one or more LEDs mayprovide a visual indicator to indicate that the physical contact wasdetected and/or that the corresponding playback device action has beenidentified and performed.

In some cases, different visual indicators, or sequence of visualindicators may be provided based on the detected physical contact and/orcorresponding playback device action. For instance, a single flash ofthe one or more LEDs may indicate that a playback volume of the playbackdevice 500 has changed, while a double flash of the one or more LEDs mayindicate that the playback device 500 (and other playback devices in thezone group with the playback device, if applicable) has skipped to anext track in the playback queue.

In another example, the playback device (and other playback devices inthe zone group with the playback device, if applicable) may play anaudio signal corresponding to identified and performed playback deviceaction. For instance, if the playback volume of the playback device 500is changed in response to a detected physical contact while the playbackdevice 500 is not playing media content, the playback device 500 mayplay a brief audio signal at the new playback volume. Other examples arealso possible.

IV. Example Playback Device Control Based on Physical Contact onPlayback Device and Orientation of Playback Device

In some example, a playback device may be positioned in differentorientations depending on how a user of the playback device wishes toplace the playback device. In some cases, an identification of aplayback device action may further be based on an orientation of theplayback device, in addition to a location of a detected physicalinteraction.

FIGS. 7A-7C show example orientations of the playback device 500. WhileFIGS. 7A-7C reference the playback device 500 of FIGS. 5A and 5B, asfurther discussed above in connection to the method 600 of FIG. 6, onehaving ordinary skill in the art will appreciate that the orientationsshown and discussed in connection to FIGS. 7A-7C, and method 800 of FIG.8 below, may also be applicable to other playback devices as well.

FIG. 7A shows a first example orientation 700 of the playback device500. As shown from a perspective facing the speaker grill 510 of theplayback device 500, the first orientation 700 may involve the firstregion 552, second region 554, and third region 556 being on a top sideof the playback device 500. As indicated above, the array of proximitysensors may further underlie the second surface 504 of the playbackdevice 500 and the third surface 506 of the playback device 500. In oneexample, a subset of the array of proximity sensors may underlie afourth region 702 on the second surface 504, and a subset of the arrayof proximity sensors may underlie a fifth region 704 on the thirdsurface 506. While in the orientation 702, the fourth region 702 may beon a left side of the playback device 500, and the fifth region 704 maybe on a right side of the playback device 500.

FIG. 7B shows a second example orientation 730 of the playback device500. As shown from the perspective facing the speaker grill 510 of theplayback device 500, the second orientation 730 may involve the firstregion 552, second region 554, and third region 556 being on the leftside of the playback device, the fifth region 704 being on the top sideof the playback device 500, and the fourth region 702 being on a bottomside of the playback device 500. In this case, the third region 556 maybe above the second region 554, which may further be above the firstregion 552.

FIG. 7C shows a third example orientation 760 of the playback device500. As shown from the perspective facing the speaker grill 510 of theplayback device 500, the third orientation 760 may involve the firstregion 552, second region 554, and third region 556 being on the rightside of the playback device, the fifth region 704 being on the bottomside of the playback device, and the fourth region 702 being on the topside of the playback device 500. In this case, the first region 552 maybe above the second region 554, which may further be above the thirdregion 556.

FIG. 8 shows an example flow diagram of a second method 800 forperforming a playback device action based on an orientation of aplayback device and a physical contact on an external surface of theplayback device. Method 800 shown in FIG. 8 presents an embodiment of amethod that can be implemented within an operating environmentinvolving, for example, the media playback system 100 of FIG. 1, one ormore of the playback device 200 of FIG. 2, one or more of the controldevice 300 of FIG. 3, one or more of the playback device 500 of FIGS. 5Aand 5B, and one or more of the playback devices 700, 730, and 760 ofFIGS. 7A, 7B, and 7C, respectively. In one example, the method 800 maybe performed by a playback device such as the playback device 200 ofFIG. 2, or the playback device of FIGS. 5A, 5B, 7A, 7B, and 7C. Inparticular, the method 800 may be performed by a processor of theplayback device, such as the processor 202 of the playback device 200,or a processor of the playback device 500. In another example, themethod 800 may alternatively be performed in whole or in part by acomputing device, such as a server in communication with the playbackdevice.

Method 800 may include one or more operations, functions, or actions asillustrated by one or more of blocks 802-808. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

As shown in FIG. 8, the method 800 involves receiving from at least oneorientation sensor, orientation data indicating an orientation of aplayback device at block 802, receiving from an array of proximitysensors, data indicating a physical contact at a location on an externalsurface of the playback device at block 804, based on at least (i) theorientation of the playback device and (ii) the location on the externalsurface, identifying a playback device action from a plurality ofplayback device actions at block 806, and causing at least the playbackdevice to perform the identified playback device action at block 808.

At block 802, the method 800 involves receiving from at least oneorientation sensor, orientation data indicating an orientation of aplayback device. As indicated previously, the playback device 500 ofFIGS. 5A, 5B, 7A. 7B, and 7C may include at least one orientationsensor. In one example, the at least one orientation sensor may includeone or more accelerometers, one or more gyroscopes, and/or one or moregeo-magnetic sensors, among other possibilities. The orientation sensormay be configured to detect an orientation of the playback device 500and output orientation data indicating the detected orientation of theplayback device 500. Accordingly, the processor of the playback device500 may receive from the at least one orientation sensor, dataindicating a current orientation of the playback device 500.

At block 804, the method 800 involves receiving from the array ofproximity sensors, location data indicating a physical contact at alocation on an external surface of the playback device. In one example,block 804 may be substantially similar to block 602 discussed above inconnection to the method 600 of FIG. 6. Accordingly, any discussionsrelating to block 602 may also be applicable to block 804.

At block 806, the method 800 involves based on at least (i) theorientation of the playback device and (ii) the location on the externalsurface, identifying a playback device action from a plurality ofplayback device actions. In one example, identifying the playback deviceaction from the plurality of playback device actions based on thelocation on the external surface may be substantially similar to block604 as shown in and discussed above in connection to the method 600 ofFIG. 6. As such, any discussions relating to block 604 may also beapplicable to block 806.

At block 806, however, the playback device action may be identified alsobased on the orientation of the playback device. In one example, thephysical contact characteristic(s) and playback device state, and thecorresponding playback device actions shown in Table 1 may be applicablewhen the playback device 500 is in the first orientation 700 shown inFIG. 7A. In one example, physical contacts at the fourth region 702 andthe fifth region 704 may correspond to playback device actions not shownin Table 1. In another example, the subset of the array of proximitysensors underlying the fourth and fifth regions 702 and 704 may bedeactivated when the playback device 500 is in the first orientation700. In further example, data received from proximity sensors in thearray of proximity sensors that underlie the fourth and fifth regions702 and 704 may be ignored by the processor when the playback device 500is in the first orientation 700. Other examples are also possible.

While the playback device 500 is in the second orientation 730, or whilethe playback device 500 is in the third orientation 760, differentplayback device actions may correspond to different physical contactcharacteristics and playback device states.

Provided in Table 2 below are illustrative examples of physical contactcharacteristics and respective playback device actions while theplayback device 500 is in the second orientation 730.

TABLE 2 Detected Physical Contact Characteristic(s) Playback andPlayback Device State Device Action 1 Tap in fifth region 704; Beginplayback Playback paused 2 Tap in fifth region 704; Pause playbackPlayback ongoing 3 Tap in first region 552 Decrease playback volume by 14 Tap in third region 556 Increase playback volume by 1 5 Touch and holdin first Decrease playback volume by region 552 2 every 160 milliseconds6 Touch and hold in third Increase playback volume by 2 region 556 every160 milliseconds 7 Double tap in fifth region 704; Begin playback ofnext track Playback paused in playback queue 8 Double tap in fifthregion 704; Skip to next track in playback Playback ongoing queue 9Swipe from left to right across Skip to next track in playback fifthregion 704 queue 10 Swipe from right to left across Skip to previoustrack in fifth region 704 playback queue 11 Dual swipe from left toright Fast forward track 15 seconds across fifth region 704 12 Dualswipe from right to left Rewind track 15 seconds across fifth region 70413 Pinch within the fifth Separate playback device from region 704 zonegroup of playback devices. 14 Stretch within the fifth Group playbackdevice with region 704 other playback devices

As shown in Table 2, and in contrast to Table 1, physical contactcharacteristics corresponding to the second region 554 may nowcorrespond to the fifth region 704, on top of the playback device 500 inthe second orientation 730. For instance, if the playback device 500 isplaying media content, a tap detected in the fifth region 704 (asopposed to the second region 554) may correspond to the playback deviceaction of pausing playback by the playback device 500. As also shown inTable 2, a tap in the first region 552 may still correspond to adecrease in the playback volume by 1, and a tap in the third region 556may still correspond to an increase in the playback volume by 1.

In one example, physical contacts at the second region 554 while theplayback device 500 is in the second orientation 730 may correspond toother playback device actions not shown in Table 2. In another example,the subset of the array of proximity sensors underlying the secondregion 554 may be deactivated when the playback device 500 is in thesecond orientation 730. In further example, data received from proximitysensors in the array of proximity sensors that underlie the secondregion 554 may be ignored by the processor when the playback device 500is in the second orientation 730.

While the playback device 500 is in the second orientation 730, theplayback device 500 may be placed on top of the fourth region 702. Assuch, the subset of the array of proximity sensors underlying the fourthregion 702 may be deactivated when the playback device 500 is in thesecond orientation 730. In further example, data received from proximitysensors in the array of proximity sensors that underlie the fourthregion 702 may be ignored by the processor when the playback device 500is in the second orientation 730. Other examples are also possible.

Provided in Table 3 below are illustrative examples of physical contactcharacteristics and respective playback device actions while theplayback device 500 is in the third orientation 760.

TABLE 3 Detected Physical Contact Characteristic(s) and Playback DeviceState Playback Device Action 1 Tap in fourth region 702; Begin playbackPlayback paused 2 Tap in fourth region 702; Pause playback Playbackongoing 3 Tap in third region Decrease playback volume by 1 4 Tap in556first region 552 Increase playback volume by 1 5 Touch and hold inthird Decrease playback volume region 556 by 2 every 160 milliseconds 6Touch and hold in first Increase playback volume region 552 by 2 every160 milliseconds 7 Double tap in fourth region 702; Begin playback ofnext Playback paused track in playback queue 8 Double tap in fourthregion 702; Skip to next track in Playback ongoing playback queue 9Swipe from left to right across Skip to next track in fourth region 702playback queue 10 Swipe from right to left across Skip to previous trackin fourth region 702 playback queue 11 Dual swipe from left to rightFast forward track 15 across fourth region 702 seconds 12 Dual swipefrom right to left Rewind track 15 seconds across fourth region 702 13Pinch within the fourth Separate playback device region 702 from zonegroup of playback devices. 14 Stretch within the fourth Group playbackdevice region 702 with other playback devices

As shown in Table 3, and in contrast to Tables 1 and 2, physical contactcharacteristics corresponding to the second region 554 in Table 1, andthe fifth region 704 in Table 2, may now correspond to the fourth region702, on top of the playback device 500 in the third orientation 760. Forinstance, if the playback device 500 is playing media content, a tapdetected in the fourth region 702 (as opposed to the second region 554or the fifth region 704) may correspond to the playback device action ofpausing playback by the playback device 500.

As also shown in Table 3, a tap in the first region 552 may nowcorrespond to an increase in the playback volume by 1, rather than adecrease in the playback volume by 1 as shown in Tables 1 and 2.Analogously, a tap in the third region 556 may now correspond to adecrease in the playback volume by 1 rather than an increase in theplayback volume by 1 as shown in Tables 1 and 2. In this case, becausethe first region 552 is physically above the third region 556 while theplayback device 500 is in the third orientation 760, having a tap in thefirst region 552 correspond to an increase volume while having a tap inthe third region 556 correspond to a decrease in volume may be moreintuitive to a user of the playback device 500.

In one example, physical contacts at the second region 554 while theplayback device 500 is in the third orientation 760 may correspond toother playback device actions not shown in Table 3. In another example,the subset of the array of proximity sensors underlying the secondregion 554 may be deactivated when the playback device 500 is in thethird orientation 760. In further example, data received from proximitysensors in the array of proximity sensors that underlie the secondregion 554 may be ignored by the processor when the playback device 500is in the third orientation 760.

While the playback device 500 is in the third orientation 760, theplayback device 500 may be placed on top of the fifth region 704. Assuch, the subset of the array of proximity sensors underlying the fifthregion 704 may be deactivated when the playback device 500 is in thethird orientation 760. In further example, data received from proximitysensors in the array of proximity sensors that underlie the fifth region704 may be ignored by the processor when the playback device 500 is inthe third orientation 760. Other examples are also possible.

One having ordinary skill in the art will appreciate that Table 2 andTable 3 are provided for illustration purposes and that other examplesare also possible.

At block 808, the method 800 involves causing at least the playbackdevice to perform the identified playback device action. In one example,block 808 may be substantially similar to block 606 discussed above inconnection to the method 600 of FIG. 6. Accordingly, any discussionsrelating to block 606 may also be applicable to block 808.

In one example, the at least one orientation sensor of the playbackdevice 500 may also detect movement of the playback device 500. In somecases, the playback device 500 may be in motion when a user is movingthe playback device 500. While moving the playback device 500, the usermay make physical contact with regions of the external surface of theplayback device 500 that have underlying proximity sensors. As such,physical contacts may be detected and playback device actions may beidentified when the user is moving the playback device 500, and notintending to provide an input to cause the playback device 500 toperform any playback device actions.

As such, in one example, if the orientation data received by theprocessor of the playback device 500 at block 802 further indicates thatthe playback device 500 is in motion, the processor may determine thatno playback device action from the plurality of playback device actionsis to be identified based on any physical contacts on the externalsurface of the playback device 500. In one case, the array of proximitysensors underlying the external surface of the playback device 500 maybe deactivated when the playback device 500 is in motion. In anothercase, data received from proximity sensors in the array of proximitysensors underlying the external surface of the playback device 500 maybe ignored by the processor when the playback device 500 is in motion.Other examples are also possible.

As indicated above, the array of proximity sensors may further beconfigured to detect presence within a proximal distance of the firstregion 552, second region 554, and third region 556 on the first surface502, the fourth region 702 on the third surface 506, or the fifth region704 on the second surface 504. In some cases, the playback device 500may be positioned such that one or more of the first surface 502, thesecond surface 504, and the third surface 506 are against a solidsurface, such as a wall or a side of a shelf. In such cases, physicalcontacts to cause the playback device 500 to perform certain playbackdevice actions may be less likely to be provided by a user via the oneor more surfaces that are against the solid surface. In such a case,based on a consistent presence detected within a proximal distance of aparticular region on the external surface of the playback device 500, asubset of the proximity sensors underlying the particular region may bedeactivated to reduce energy consumption of the playback device 500. Inone instance, the deactivated subset of the proximity sensors may bereactivated when an orientation of the playback device 500 has changed,or if the playback device 500 has been moved. Other examples are alsopossible.

While discussions herein generally refer to a physical interaction withthe external surface of the playback device as a physical contact withthe external surface of the playback device, one having ordinary skillin the art will appreciate that the physical interaction, as indicatedpreviously, may additionally or alternatively be a physical presencewithin a predetermined proximal distance from the external surface ofthe playback device.

V. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of aninvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

What is claimed is:
 1. A playback device comprising: an enclosurecomprising a first external surface where speakers of the playbackdevice are positioned, a second external surface, a third externalsurface, and a fourth external surface, where: the second, third, andfourth external surfaces intersect the first external surface; and theenclosure is configured to be placed in at least two orientations,where: in a first orientation the enclosure rests on the fourth externalsurface, the third external surface forms a lateral surface of theplayback device, and the second external surface forms a top surface ofthe playback device; and in a second orientation the enclosure rests onthe second external surface, the third external surface forms a lateralsurface of the playback device, and the fourth external surface forms atop surface of the playback device; an array of proximity sensorsunderlying the third external surface of the playback device; anorientation sensor; a processor; and memory having stored thereoninstructions executable by the processor for causing the processor toperform functions comprising: receiving orientation data from theorientation sensor indicating an orientation of the playback device;receiving data indicating detection of a user input, where the detecteduser input comprises a swipe from a first location on the array ofproximity sensors to a second location on the array of proximitysensors; in response to receiving the data indicating detection of auser input comprising a swipe from the first location to the secondlocation, causing a playback volume of the playback device to change,wherein: the change in playback volume comprises an increase in playbackvolume when the orientation data indicates that the enclosure is in thefirst orientation, and the change in playback volume comprises adecrease in playback volume when the orientation data indicates that theenclosure is in the second orientation.
 2. The playback device of claim1, wherein in the second orientation the third external surface forms aright lateral surface of the playback device.
 3. The playback device ofclaim 1, wherein the orientation sensor comprises at least oneaccelerometer.
 4. The playback device of claim 1, wherein the firstorientation is a first vertical orientation and the second orientationis a second vertical orientation.
 5. The playback device of claim 1,wherein the user input is a first user input, and wherein the functionsfurther comprise: while the playback device is playing audio content,receiving data indicating a second user input, the second user inputcomprising a physical contact at a third location on the array ofproximity sensors; in response to receiving the data indicating thesecond user input, causing the playback device to pause playback ofaudio content.
 6. The playback device of claim 5, and wherein thefunctions further comprise: while the playback device is not playingaudio content, receiving data indicating a third user input, the thirduser input comprising a physical contact at the third location on thearray of proximity sensors; in response to receiving the data indicatingthe third user input, causing the playback device to begin playback ofaudio content.
 7. The playback device of claim 5, wherein the thirdlocation is the same as the first location.
 8. The playback device ofclaim 5, wherein the third location is the same as the second location.9. A tangible, non-transitory computer-readable medium having storedtherein instructions executable by one of more processors for causing aplayback device to perform functions comprising: receiving orientationdata from an orientation sensor indicating an orientation of theplayback device; receiving data indicating detection of a user input,where the detected user input comprises a swipe from a first location onan array of proximity sensors to a second location on the array ofproximity sensors, wherein the playback device comprises an enclosurecomprising a first external surface where speakers of the playbackdevice are positioned, a second external surface, a third externalsurface, and a fourth external surface, where: the second, third, andfourth external surfaces intersect the first external surface; and theenclosure is configured to be placed in at least two orientations,where: in a first orientation the enclosure rests on the fourth externalsurface, the third external surface forms a lateral surface of theplayback device, and the second external surface forms a top surface ofthe playback device; and in a second orientation the enclosure rests onthe second external surface the third external surface forms a lateralsurface of the playback device, and the fourth external surface forms atop surface of the playback device; and wherein the array of proximitysensor underlie the third external surface of the playback device; andin response to receiving the data indicating detection of a user inputcomprising a swipe from the first location to the second location,causing a playback volume of the playback device to change, wherein; thechange in playback volume comprises an increase in playback volume whenthe orientation data of the playback device indicates that the enclosureis in the first orientation, and the change in playback volume comprisesa decrease in playback volume when the orientation data indicates thatthe enclosure is in the second orientation.
 10. The tangible,non-transitory computer-readable medium of claim 9, wherein the firstphysical contact at the first location followed by the second physicalcontact at the second location indicates a swipe gesture from the firstlocation to the second location along the second external surface of theplayback device.
 11. The tangible, non-transitory computer-readablemedium of claim 9, wherein the orientation sensor comprises at least oneaccelerometer.
 12. The tangible, non-transitory computer-readable mediumof claim 9, wherein the first orientation is a first verticalorientation and the second orientation is a second vertical orientation.13. The tangible, non-transitory computer-readable medium of claim 9,where in the user input is a first user input, and wherein the functionsfurther comprise: while the playback device is playing audio content,receiving data indicating a second user input, the second user inputcomprising a physical contact at a third location on the array ofproximity sensors; and in response to receiving the data indicating thesecond user input, causing the playback device to pause playback ofaudio content.
 14. The tangible, non-transitory computer-readable mediumof claim 13, and wherein the functions further comprise: while theplayback device is not playing audio content, receiving data indicatinga third user input, the third user input comprising a physical contactat the third location on the array of the proximity sensors; and inresponse to receiving the data indicating the third user input, causingthe playback device to begin playback of audio content.
 15. The methodto be performed by a playback device comprising an enclosure thatcomprises: a first external surface where speakers of the playbackdevice are positioned, a second external surface, a third externalsurface, and a fourth external surface, where: the second, third, andfourth external surfaces intersect the first external surface; and theenclosure is configured to be placed in at least two orientations,where: in a first orientation the enclosure rests on the fourth externalsurface, the third external surface forms a lateral surface of theplayback device, and the second external surface forms a top surface ofthe playback device; and in a second orientation the enclosure rests onthe second external surface the third external surface forms a lateralsurface of the playback device, and the fourth external surface forms atop surface of the playback device; an array of proximity sensorsunderlying the third external surface of the playback device; and anorientation sensor; the method comprising: receiving orientation datafrom the orientation sensor indicating an orientation of the playbackdevice; receiving data indicating detection of a user input, where thedetected user input comprises a swipe from a first location on the arrayof proximity sensors to a second location on the array of proximitysensors; and in response to receiving the data indicating detection of auser input comprising a swipe from the first location to the secondlocation, causing a playback volume of the playback device to change,wherein: the change in playback volume comprises an increase in playbackvolume when the orientation data indicates that the enclosure is in thefirst orientation, and the change in playback volume comprises adecrease in playback volume when the orientation data indicates that theenclosure is in the second orientation.
 16. The method of claim 15,wherein the first physical contact at the first location followed by thesecond physical contact at the second location indicates a swipe gesturefrom the first location to the second location along the second externalsurface of the playback device.
 17. The method of claim 15, wherein theorientation sensor comprises at least one accelerometer.
 18. The methodof claim 15, wherein the first orientation is a first verticalorientation and the second orientation is a second vertical orientation.19. The method of claim 15, wherein the user input is a first userinput, and wherein the method further comprises: while the playbackdevice is playing audio content, receiving data indicating a second userinput, the second user input comprising of a physical contact at a thirdlocation on the array of proximity sensors; and in response to receivingthe data indicating the second user input, causing the playback deviceto pause playback of audio content.
 20. The method of claim 19, furthercomprising: while the playback device is not playing audio content,receiving data indicating a third user input, the third user inputcomprising a physical contact at the third location on the array ofproximity sensors; and in response to receiving data indicating thethird user input, causing the playback device to begin playback of audiocontent.